Komputer for Alle 1999 #5

home *** CD-ROM | disk | FTP | other *** search

/ Komputer for Alle 1999 #5 / 1999 CD 5 (black).iso / Delphi3 / README.TXT < prev next >

Wrap

Text File | 1997-08-04 | 20.0 KB | 543 lines

Welcome to the Delphi 3 Standard Edition Contents: WHERE TO FIND INFORMATION CONTACTING BORLAND CD-ROM DIRECTORY OVERVIEW DEMO APPLICATIONS INTRABUILDER TRIAL C++BUILDER TRIAL DOCUMENTATION UPDATES KNOWN PROBLEMS WHERE TO FIND INFORMATION This file contains last-minute information about Delphi 3. ********************************************************* Before distributing applications developed with Delphi, please read the guidelines in DEPLOY.TXT (on the Delphi CD or in the Delphi 3 directory). ********************************************************* For installation instructions and minimum system requirements, see INSTALL.TXT (on the Delphi CD or in the Delphi 3 directory). For an overview of Delphi and a list of new features, select Help|What's New from the Delphi main menu. For information about migrating from previous releases of Delphi, including maintenance of legacy applications and installation of third-party components, see the Compatibility With Version 2 topic in the online Help. For detailed documentation, see the online Help and printed manuals that accompany this release. Additional documents are on the Delphi CD in the INFO\BORLAND directory. Check Borland's Web site at http://www.borland.com/ for documentation updates and other information. NOTE: All printed and online documentation assume that you have installed Delphi using the default directory structure. Online Resources ---------------- You can get information from any of these online sources: World Wide Web: http://www.borland.com/ FTP: ftp.borland.com Technical documents available by anonymous ftp. Listserv: To subscribe to electronic newsletters, use the online form at http://www.borland.com/feedback/listserv.html or, for Borland's international listserver, http://www.borland.com/feedback/intlist.html. TECHFAX 1-800-822-4269 (North America) Technical documents available by fax. World Wide Web -------------- Check Borland's Web site regularly. The Delphi Product Team will post white papers, competitive analyses, answers to frequently asked questions, sample applications, updated software, and information about new and existing products. You may want to check these URLs in particular: http://www.borland.com/delphi/ http://www.borland.com/techsupport/delphi/ http://www.borland.com/techsupport/delphi/downloads/ (updated Help, software, and other files) http://www.borland.com/delphi/cpp/ (information for C++ programmers) http://www.borland.com/delphi/vb/ (information for Visual Basic programmers) http://www.borland.com/newsgroups/ (see below) Newsgroups ---------- Borland Online hosts a variety of newsgroups where users can exchange information about Borland development tools and their use. For a complete list, see http://www.borland.com/newsgroups/. In addition to the groups hosted by Borland Online, the following Usenet groups are devoted to Delphi and related programming issues. (These newsgroups are maintained by users and are not official Borland sites.) news:comp.lang.pascal.delphi.misc news:comp.lang.pascal.delphi.components news:comp.lang.pascal.delphi.components.misc news:comp.lang.pascal.delphi.components.usage news:comp.lang.pascal.delphi.components.writing news:comp.lang.pascal.delphi.databases news:comp.lang.pascal.delphi.advocacy news:comp.lang.pascal.delphi.announce news:comp.lang.pascal.borland CONTACTING BORLAND Installation Assistance and Developer Support --------------------------------------------- Borland offers a range of support services for Delphi and other tools. For information, see our World Wide Web site at http://www.borland.com/. For assistance outside of North America, contact your local Borland representative. For a list of offices and distributors world-wide, see http://www.borland.com/bww/. CD-ROM DIRECTORY OVERVIEW The Delphi CD ROM includes the following files and directories. [root] Contains files used for installation and registration as well as these important documents: INSTALL.TXT Installation instructions. README.TXT Release notes, last-minute documentation, and a list of known problems. LICENSE.TXT The Delphi license agreement. DEPLOY.TXT Information about deploying Delphi applications. \INSTALL Contains the setup program and related files. \INFO Contains subdirectories with information and third-party demo products. The \INFO\EXTRAS directory contains source code and other files for JPEG and FIF graphics formats, and for data-compression algorithms; for more information, see INFO\EXTRAS\EXTRAS.TXT. \IE3 Contains Microsoft's Internet Explorer 3.02. \TRIALS Contains trial versions of the IntraBuilder Web application development tool (in \TRIALS\INTRABLD) and of C++Builder, Borland's rapid application development tool for C++ programmers (in \TRIALS\CBUILDER). \ISXPRESS Contains InstallShield Express, a customized application deployment tool for Delphi 3, the BDE, and related software. \RUNIMAGE Contains a complete Delphi installation. All files are unpacked and in the default directory structure. \DELPHI16 Contains the last 16-bit release of Delphi (version 1.02). Run SETUP.EXE (in the \DELPHI16\INSTALL subdirectory) to install. DEMO APPLICATIONS Sample programs are installed with Delphi in the Delphi 3\Demos\... directory. To build these demos, compile the appropriate .DPR file. RichEdit (in ...\Richedit) demonstrates the TRichEdit control. ...\DEMOS\DB contains additional database sample projects. Data used by these examples is in ...\DEMOS\DATA. ...\DEMOS\DOC contains sample projects from the printed documentation. ...\DEMOS\DATA contains data used by sample programs. INTRABUILDER TRIAL The Delphi CD includes a free 30-day trial edition of Borland's IntraBuilder. IntraBuilder is a visual JavaScript toolset that has everything you need to build and maintain live, data-driven Web applications and run them on your Web server. To view a self-running demo, or to install the trial version of IntraBuilder, run SETUP.EXE in the \TRIALS\INTRABLD directory of the Delphi CD. For more information about IntraBuilder, see http://www.borland.com/intrabuilder/. C++BUILDER TRIAL The Delphi CD includes a trial edition of C++Builder, Borland's rapid application development tool for C++ programming. To install the trial version of C++Builder, run SETUP.EXE in the \TRIALS\CBUILDER\SETUP directory of the Delphi CD. For more information about C++Builder, see http://www.borland.com/bcppbuilder/ DOCUMENTATION UPDATES VCL documentation and online Help --------------------------------- The VCL reference material in the online Help is more up to date than the printed version. The following methods are documented only online: TApplication.NormalizeAllTopMosts TCustomForm.WantChildKey (overridden in TActiveForm) TOleContainer.SaveAsDocument The correct syntax for the TApplication.MessageBox method is in the online Help. Help entries for the TTable, TImage, and TBDEDataSet objects, among others, have also been revised. Due to limitations in the WinHelp compiler, Windows API Help topics do not appear in the Delphi Help index. However, these topics are available from the Delphi IDE's context-sensitive Help system; if you select a Windows API function in the Code editor and press F1, the appropriate Windows Help topic will appear. To see an index of Windows API Help topics, access the Windows API Help directly. The easiest way to do this is to add a button to the speedbar: Right-click on the speedbar and select Properties to open the Speedbar editor; select Help from the Categories list and drag the Windows API Help icon from the Commands list to your speedbar; then close the Speedbar editor. Components on the Win 3.1 palette page are not linked to the context-sensitive online Help system. For documentation on these legacy components, refer to the DELPHI.HLP file located in \Delphi16\Runimage\Delphi\Bin on your Delphi CD. Two components on the ActiveX palette page are not linked to the context-sensitive online Help system. For documentation on the VtChart control, see Delphi 3\OCX\Vci\Impress\Vcfi.hlp. For documentation on the Graph Custom Control, see Delphi 3\OCX\Pinnacle\Graph.hlp. Some database example programs contain hard-coded directory paths. To make these examples compile, you may need to change the directory paths. Asian calendar eras ------------------- RTL functions provide increased support for Asian calendar eras. Conversion functions like StrToDate and DateToStr now preserve information about eras. TRegistry --------- Under Windows NT, TRegistry can now open and read from the registry even if the user does not have administrative rights. COMCTL32 -------- Several of the components on the Win32 palette page function best with the latest version (4.70) of COMCTL32.DLL. TCoolBar and TDateTimePicker will not work at all unless version 4.70 or later is installed. In addition, the following properties require version 4.70: TToolBar.DisabledImages TToolBar.Flat TToolBar.HotImages TToolBar.Images TTabControl.HotTrack TTabControl.ScrollOpposite TTabControl.TabPosition TPageControl.HotTrack TPageControl.ScrollOpposite TPageControl.TabPosition TListView.Checkboxes TListView.HotTrack TListView.GridLines TListView.RowSelect TListItem.Checked The Min, Max, and Position properties of TProgressBar must fall within the range of 0 - 65535 if the installed version of COMCTL32.DLL is less than 4.70. Win32 shell extensions ---------------------- Win32 shell extensions require that the threading model for the extension object be set to "Apartment" in the system registry. Since TComObjectFactory.UpdateRegistry doesn't make this entry automatically, you can do it manually by inserting the Value Name "ThreadingModel" with the Value "Apartment" under the CLSID key for your control in the registry. You can also override TComObjectFactory.UpdateRegistry to do this work for you; the following example code is for a Copy Hook shell extension: procedure TCopyHookFactory.UpdateRegistry(Register: Boolean); var ClsID: string; begin ClsID := GUIDToString(ClassID); inherited UpdateRegistry(Register); if Register then begin CreateRegKey('CLSID\' + ClsID, 'ThreadingModel', 'Apartment'); CreateRegKey('directory\shellex\CopyHookHandlers\' + ClassName, '', ClsID); end else DeleteRegKey('directory\shellex\CopyHookHandlers\' + ClassName); end; Using OpenGL ------------ Applications or libraries that use the OpenGL graphics libraries must ensure that the 8087 control word is set to mask Overflow, Zero Divide, and Invalid Operation exceptions. This is done automatically in the OPENGL unit, but if your application does not use the OPENGL unit (for example, if you are using an ActiveX control that employs OpenGL), you can do this by including the following line in the initialization code of a unit: Set8087CW($133F); Borland Database Engine ----------------------- A Driver Development Kit is available for the BDE. Contact Developer Relations at Borland for details. SNoTableName and other constants have been moved to the BDEConst unit. IDAPI functions such as DbiQExecProcDirect and DbiOpenSPParamList now support Access named queries, which the BDE treats as stored procedures. You can now set the Access SystemDB (workgroup information file) on a per-database basis using the BDE Administrator. The Access driver now supports referential integrity. To switch a cursor's Access locking protocol between pessimistic and optimistic, toggle the Boolean curPESSIMISTICLOCKS property with DbiSetProp. Using JPEG Images ----------------- To use JPEG images at design time, choose Component | Install Component, create a new package, select JPEG as the Unit File Name, and install the package. To use JPEGs in an application at runtime, include the JPEG unit in your unit's "uses" clause. VCL Help Files -------------- The VCL Help file (VCL3.HLP) uses another file called VCL3JUMP.HLP to provide context-sensitive jump support. Do not delete this file. If you accidentally delete it, you'll have to restore it from the Delphi CD. Overriding Resource-Module Localization --------------------------------------- At start-up, applications typically check the locale of the system and look for a resource module that matches the language and country. If you want your application to use a different resource module from the one indicated, you can set an override in the registry: Under the HKEY_Current_User\Software\Borland\Delphi\Locales key, add your application's path and filename as a string value and set the data value to the extension of your resource modules; at startup, your application will look for resource modules with this extension before using the system locale. For more information, see "Using Resource Modules" under the "Localizing Resources" Help topic. KNOWN PROBLEMS Installation and Un-installation -------------------------------- Existing IDAPI32.CFG alias information is not changed by the Delphi 3 installation. Therefore it may be necessary to change the path in the DefaultDD alias to the Delphi 3 data dictionary. Un-installing Delphi 2 or the C++Builder trial version can remove some Delphi 3 settings and delete components from the palette. We recommend reinstalling Delphi 3 after un-installation of Delphi 2 or C++Builder. The NetManage Internet Control Pack installed with Delphi is also shipped with other applications, including Visual Basic and PowerBuilder. These components may be unregistered in the process of un-installing another product. If this happens, reinstall Delphi. After installing the C++Builder trial version, you may need to reset some alias information in the default IDAPI32.CFG. Specifically, the SERVER NAME for the IBLOCAL alias should point to C:\Program Files\Borland\Delphi 3\Demos\Data\EMPLOYEE.GDB. It's a good idea to back up your IDAPI32.CFG before installing C++Builder. Integrated Development Environment and VCL ------------------------------------------ TToolButton components don't resize properly when images in the TToolBar's ImageList property are modified. To work around this problem, remove images from the ImageList before modifying them; then replace them in the ImageList. Due to a problem in Microsoft's COMCTL32.DLL, the Arrange method in TListView does not function. This makes it difficult to clean up the list's alignment when ViewStyle is vsIcon or vsSmallIcon, but otherwise does not affect the behavior of the component. Use check boxes in TListView only when ViewStyle is set to vsList or vsReport. The TLabel.ParentFont property is not used under Windows NT 4.0. The fsStayOnTop setting for TForm.FormStyle does not function correctly when one fsStayOnTop form launches another. In this case, neither form will consistently remain on top. Due to an operating-system bug, the TImageList.ResourceLoad method does not load Icon or Cursor files. If you set TOpenDialog.AllowMultiSelect to True under Windows NT 4.0, a maximum of 20 files are returned. This bug is fixed in Service Pack 2 (available from Microsoft). Database -------- The BDE no longer supports DbiUseIdleTime. Use DbiSaveChanges instead. Local SQL queries require a table qualifier or alias name if the field name is in quotation marks. Examples: (BAD) select name AS "First Name" from customer (OK) select name AS customer."First Name" from customer (OK) select name AS c."First Name" from customer c When you use cached updates, changes made to indexed table fields are not reflected until the updates are applied. If you use cached updates with master/detail tables, TQuery will re-execute the detail query each time the master record moves. The floating-point format required for custom constraints is inconsistent with international Windows settings. Always use periods (.) for decimals in custom constraints. Access Driver ------------- Some functionality is not yet implemented in this release. BCD (binary coded decimal) support is not available. Key-violation tables cannot be created with DbiAddIndex. (All other DbiAddIndex functionality is supported.) QBE, heterogeneous queries, and queries using the local SQL engine are not supported. In the SDK, DbiDoRestructure and DbiRegenIndex are not available. The Access driver does not support DAO 3.5 (Access 97). If you upgrade Access 95 to Access 97, DAO 3.0 still resides on your machine, so the driver will function correctly. If you install Access 97 with no prior version of Access 95, the driver will not function. Because DAO 3.0 (Access 95) is not thread-safe, all database functions must occur in the application's primary thread. MS Access does not support opening a table that has already been opened exclusively. Hence opening a table when TTable.Exclusive is set to True prevents the user from opening that table again, even in same session. Use a BLOB as a parameter in a query only if the BLOB data is less than 256 bytes. When the Database Desktop copies an InterBase table to Access, the table and data are copied without indexes. If the table includes an index, you'll see an "invalid parameter" error. Use the Data Pump for this purpose instead. When borrowing a structure from a Paradox table, the Database Desktop does not copy primary indexes to the resultant Access table. Use the Data Pump for this purpose instead. AUTOINCREMENT fields do not update correctly when records are added to a table that has at least one other field with a default value. QuickReports ------------ Due to limitations in the conversion process, some complex reports from Delphi 2 may not load properly. Dynamically Loaded Libraries ---------------------------- Windows NT sometimes incorrectly unloads a library when another library that depends on it fails to load. This problem occurs only when libraries are loaded dynamically under the conditions described below. It affects Windows NT 3.51; Service Pack 2 fixes the bug for Windows NT 4.0. The problem arises when a dynamically loaded library uses two other libraries, each of which in turn uses another library. Suppose, for example, that an application uses five DLLs that are loaded dynamically in the following order: DLL1, DLL2, DLL3, DLL4, DLL5. Suppose that the following dependencies hold among the DLLs: DLL5 uses DLL4; DLL4 uses DLL3. DLL5 uses DLL2; DLL2 uses DLL1. Suppose the first three DLLs (DLL1-3) load successfully, but DLL4 calls an entry point in DLL3 that has been removed. In this case, DLL5 will naturally fail to load. If a second attempt is made to load the library, Windows will unload DLL1 and the application program may crash. This problem can affect installation of packages within the Delphi IDE; it does not affect deployed applications, where packages are statically loaded. If you are using Delphi under Windows NT 3.51, the best way to avoid the problem is to make sure all required packages are updated before you recompile or install components. ---------------------------------------------------------------- Unless otherwise noted, all materials provided in this release are Copyright 1983 - 1997 by Borland International. ----------------------------- END ------------------------------